Sending verification password responsive to mobile device proximity

ABSTRACT

A method includes detecting proximity between a mobile device and a remote device associated with a transaction reserved by a user of the mobile device. A verification password is sent to the remote device responsive to detecting the proximity. A device includes a module to detect proximity between the device and a remote device associated with a transaction reserved by a user of the device and a processor coupled to the module. The processor is to send a verification password to the remote device responsive to detecting the proximity.

BACKGROUND Field of the Disclosure

The disclosed subject matter relates generally to mobile computing systems and, more particularly, to the sending of a verification password responsive to mobile device proximity.

Description of the Related Art

Mobile devices are being increasingly used to handle commercial transactions without the need for separate credit card or other payment processing. In some instances, verification passwords are employed to provide an additional level of identity security. For example, a user may transact for transportation using an application on the mobile device. When completing the reservation, the user may be provided with a verification password, such as a one-time password (OTP). Upon entering the vehicle, the user may orally communicate the verification password to the driver, who enters the verification password into a different mobile device, thereby verifying the identity of the passenger and initiating the service. Upon completion of the transportation service, the rider is automatically billed in accordance with the previously registered payment arrangements. Thus, the user may reserve and complete the transport service without the need to manage separate payment arrangements. The use of the verification password provides additional security for the passenger, as it verifies that the transportation service was properly handled. One potential inconvenience with the use of verification passwords in this context is that it requires the rider to access the mobile device to retrieve the password, preventing the user from employing the device for a call or other activity.

Another type of service that may employ a verification password is a delivery service. When a user transacts for a delivery, a verification password is provided. When the delivery is made, the user may provide the verification password to the delivery person, thereby authenticating the transaction. This approach also provides additional security for both the individual ordering the delivery and the delivery vendor, as the user's identity and delivery location are verified. However, such an approach may be inconvenient for the user as the mobile device would have to be accessed to search for the authentication password. The transaction for the goods being delivered may be conducted hours, days, or even weeks prior to the actual delivery. It may be difficult for the user to locate the verification password in the mobile device at the time of delivery. In some instances, the user may have inadvertently deleted the message containing the verification password, causing additional delay and inconvenience for the user, as the delivery service may have to be contacted to retrieve the verification password or to generate a new one.

The present disclosure is directed to various methods and devices that may solve or at least reduce some of the problems identified above.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure may be better understood, and its numerous features and advantages made apparent to those skilled in the art by referencing the accompanying drawings.

FIG. 1 is a simplified block diagram of a mobile device operable for automatically communicating or displaying verification passwords, according to some embodiments disclosed herein;

FIG. 2 is a simplified flow diagram of a method for communicating a verification password based on mobile device proximity, according to some embodiments disclosed herein;

FIG. 3 is a simplified flow diagram of a method for displaying a verification password based on expected appointment time window, according to some embodiments disclosed herein; and

FIG. 4 is a front view of the device of FIG. 1 illustrating an example notification list that includes a verification password and expected service time, according to some embodiments disclosed herein.

The use of the same reference symbols in different drawings indicates similar or identical items.

DETAILED DESCRIPTION OF EMBODIMENT(S)

FIGS. 1-4 illustrate example techniques for automatically processing verification passwords for a user of a mobile device. In some embodiments, device context information such as location, travel mode, proximity to another mobile device, etc. may be employed to verify that the user is engaging in a previously contracted point-of-service (POS) transaction associated with a verification password (e.g., a one-time password (OTP)). For example, the POS transaction may be associated with a transportation service (e.g., taxi or ride sharing). The verification password may be communicated to a service provider automatically based on the context information. In some embodiments, the user may contract for a time window transaction having an associated verification password. For example, a time window transaction may include a delivery transaction. The verification password and an expected service completion window may be extracted from a document associated with the time window transaction, and the verification password may be automatically displayed on the mobile device proximate the service completion window.

FIG. 1 is a simplistic block diagram of a device 100. The device 100 implements a computing system 105 including, among other things, a processor 110, a memory 115, a microphone 120, a speaker 125, a display 130, a motion sensor 132 (e.g., accelerometer, magnetometer, mercury switch, gyroscope, compass, or some combination thereof), a proximity communication module 135 (e.g., RFID or NFC), and a location module 140 (e.g., global positioning system (GPS) module, Wi-Fi location module, etc.). The memory 115 may be a volatile memory (e.g., DRAM, SRAM) or a non-volatile memory (e.g., ROM, flash memory, hard disk, etc.). The device 100 includes a transceiver 145 for transmitting and receiving signals via an antenna 150 over a communication link. The transceiver 145 may include one or more radios for communicating according to different radio access technologies, such as cellular, Wi-Fi, Bluetooth®, etc. The communication link may have a variety of forms. In some embodiments, the communication link may be a wireless radio or cellular radio link. The communication link may also communicate over a packet-based communication network, such as the Internet. In one embodiment, a cloud computing resource 155 may interface with the device 100 to implement one or more of the functions described herein.

In various embodiments, the device 100 may be embodied in a handheld or wearable device, such as a laptop computer, a handheld computer, a tablet computer, a mobile device, a telephone, a personal data assistant, a music player, a game device, a wearable computing device and the like. To the extent certain example aspects of the device 100 are not described herein, such example aspects may or may not be included in various embodiments without limiting the spirit and scope of the embodiments of the present application as would be understood by one of skill in the art.

In the device 100, the processor 110 may execute instructions stored in the memory 115 and store information in the memory 115, such as the results of the executed instructions. Some embodiments of the processor 110 and the memory 115 may be configured to implement a transaction verification application 160. The transaction verification application 160 performs various functions to identify and track verification passwords associated with transactions contracted by a user of the mobile device 100. The transaction verification application 160 may maintain a transaction list 165 identifying point-of-service (POS) or time window transactions contracted by the user of the mobile device 100. The transaction verification application 160 may automatically extract the information for the transactions from applications (e.g., a POS application 170 for contracting transportation services) executed on the mobile device 100, messages received on the mobile device 100 (e.g., email or text), or web documents (e.g., web pages) viewed on the mobile device 100.

FIG. 2 is a simplified flow diagram of a method 200 for communicating a verification password based on mobile device proximity, according to some embodiments disclosed herein. In the example illustrated in FIG. 2, the transactions may be POS transactions, such as transportation services.

In method block 205, the transaction verification application 160 extracts transaction information, including a verification password and a transaction location. The transaction verification application 160 may store the extracted information in the transaction list 165. In some embodiments, the user may execute the POS application 170 to contract for the POS service. In some embodiments, the transaction verification application 160 may interface with the POS application 170 to receive the transaction details, or it may be integrated into the POS application 170. In some embodiments, the transaction verification application 160 may extract the transaction details from documents associated with the transaction. For example, the transaction may be completed using a web page, or the service provider may send transaction details via email or text message. As used herein, the term document refers to a web page, email message, or text message received by the mobile device 100 associated with the transaction.

In method block 210, the transaction verification application 160 detects proximity to a remote device operated by the service provider. In some embodiments, the proximity may be determined using device context information such as the device location information provided by the location module 140 (see FIG. 1). The device location may be compared to the transaction location (e.g., pickup location) to determine proximity. In some embodiments, the mobile device 100 may communicate with the service provider device to indicate proximity. For example, the mobile device 100 may communicate to the service provider device using RFID or NFC communication via the proximity communication module 135 (see FIG. 1). The mobile device 100 may read an RFID tag associated with the service provider device. The proximity communication may also be linked to the device location and transaction location in that the transaction verification application 160 may search for the service provider device when the mobile device 100 is in the transaction location.

In some embodiments, the mobile device 100 may employ additional context data in addition to the location data. In method block 215, the transaction verification application 160 determines whether context information associated with the device 100 indicates transaction engagement. This additional context information may provide assurance not only that the user is near the service provider, but that the user has also engaged in the transaction. If only location information were employed, the driver could drive off without the passenger and still appear to complete the transaction.

In one embodiment, the context information includes a motion mode of the device 100. For example, the mobile device 100 may identify modes of the device 100 such as walking, stationary, driving, etc. The device 100 may use motion data from the motion sensor 132 to determine the mode. The transaction verification application 160 may verify the transaction engagement in method block 215 based on a transition from a walking mode to a driving mode.

In one embodiment, the context information includes a noise profile of the device 100. For example, the mobile device 100 may monitor the microphone 120 (see FIG. 1) and compare the current noise profile to a library of reference noise profiles. For example, the noise profile may match an outdoors reference profile if the user is outdoors walking to the transaction location. The noise profile may match a vehicle reference profile if the user is in a vehicle (e.g., less ambient noise). The transaction verification application 160 may verify the transaction engagement in method block 215 based on a transition from an outdoor noise profile to a vehicle noise profile.

In some embodiments, the transaction verification application 160 may evaluate both the motion mode and the noise profile in method block 215.

Upon identifying transaction engagement in method block 215, the transaction verification application 160 sends the verification password to the service provider device in method block 220. The verification password may be sent via text message, by the POS application 170, via peer-to-peer message, via audio message (e.g., audible or encoded), via infrared message, etc.

Automatically extracting the verification password and providing it to the service provided based on device context (e.g., location, motion mode, noise profile, etc.) greatly simplifies the process the user employs to complete the transaction. The user does not have to interact with the device 100 to find the verification password or interrupt other uses of the device 100. When the transaction is engaged, the verification password is automatically communicated to the service provider.

FIG. 3 is a simplified flow diagram of a method 300 for retrieving a verification password based on expected appointment time window, according to some embodiments disclosed herein. In the example illustrated in FIG. 3, the transactions may be time transactions, such as delivery services.

In method block 305, the transaction verification application 160 extracts transaction information, including a verification password and a service time. The transaction verification application 160 may store the extracted information in the transaction list 165. In some embodiments, the transaction verification application 160 may extract the transaction details from documents associated with the transaction. For example, the transaction may be completed using a web page, or the service provider may send transaction details via email or text message. As used herein, the term document refers to a web page, email message, or text message received by the mobile device 100 associated with the transaction.

In some embodiments, the transaction verification application 160 may update the expected service time based on new information received in the device 100 (e.g., text message, emails, etc.) indicating a more accurate service time, a change to the service time, etc.

In method block 310, the transaction verification application 160 determines that the current time is proximate the service time. For example, transaction verification application 160 may determine that the current time is within a particular time window relative to the expected service time. The size of the time window may depend on the information extracted regarding the transaction. If the service provider indicates only a particular day for the service, the time window may be the associated day. If a more refined time window is provided, a shorter time window may be employed. The time window may also be updated based on updates provided by the service provider on the service time.

The transaction verification application 160 provides the verification password on the display 130 in method block 315 responsive to detecting service time proximity in method block 310. In some embodiments, the transaction verification application 160 may send a notification message to the user.

FIG. 4 is a front view of the device 100 of FIG. 1 illustrating an example notification list 400. The notification list 400 includes the verification password 405 and the expected service time 410. The notification list 400 may also include additional notification information, such as recent messages, calls, mail, etc. The notification list 400 may be provided in a low power AoD state, where the device 100 is locked and full functionality is not present. In such a state, the functionality of the device 100 may be limited (e.g., receiving calls or messages, and providing status information on the display 130). The user simply has to look at the display during the service time window or when the delivery arrives to see the verification password. The user does not have to unlock the device 100 or search for the transaction to retrieve the verification password. In some embodiments, the notification list including the verification password may also be provided in a fully-active mode of the device 100.

Providing the verification password on the display 130 proximate the service time greatly simplifies the process the user employs to complete the transaction. The user does not have to interact with the device 100 to find the verification password or other details of the transaction. When the appropriate time period arrives, the user is provided with the associated verification password.

A method provided includes detecting proximity between a mobile device and a remote device associated with a transaction reserved by a user of the mobile device and sending a verification password to the remote device responsive to detecting the proximity.

A device provided includes a module to detect proximity between the device and a remote device associated with a transaction reserved by a user of the device and a processor coupled to the module. The processor is to send a verification password to the remote device responsive to detecting the proximity.

In some embodiments, certain aspects of the techniques described above may be implemented by one or more processors of a processing system executing software. The techniques described herein may be implemented by executing software on a computing device, such as the processor 110 of FIG. 1, however, such methods are not abstract in that they improve the operation of the device 100 and the user's experience when operating the device 100. Prior to execution, the software instructions may be transferred from a non-transitory computer readable storage medium to a memory, such as the memory 115 of FIG. 1.

The software may include one or more sets of executable instructions stored or otherwise tangibly embodied on a non-transitory computer readable storage medium. The software can include the instructions and certain data that, when executed by one or more processors, manipulate the one or more processors to perform one or more aspects of the techniques described above. The non-transitory computer readable storage medium can include, for example, a magnetic or optical disk storage device, solid state storage devices such as Flash memory, a cache, random access memory (RAM) or other non-volatile memory device or devices, and the like. The executable instructions stored on the non-transitory computer readable storage medium may be in source code, assembly language code, object code, or other instruction format that is interpreted or otherwise executable by one or more processors.

A computer readable storage medium may include any storage medium, or combination of storage media, accessible by a computer system during use to provide instructions and/or data to the computer system. Such storage media can include, but is not limited to, optical media (e.g., compact disc (CD), digital versatile disc (DVD), Blu-Ray disc), magnetic media (e.g., floppy disc, magnetic tape or magnetic hard drive), volatile memory (e.g., random access memory (RAM) or cache), non-volatile memory (e.g., read-only memory (ROM) or Flash memory), or microelectromechanical systems (MEMS)-based storage media. The computer readable storage medium may be embedded in the computing system (e.g., system RAM or ROM), fixedly attached to the computing system (e.g., a magnetic hard drive), removably attached to the computing system (e.g., an optical disc or Universal Serial Bus (USB)-based Flash memory), or coupled to the computer system via a wired or wireless network (e.g., network accessible storage (NAS)).

The particular embodiments disclosed above are illustrative only, as the invention may be modified and practiced in different but equivalent manners apparent to those skilled in the art having the benefit of the teachings herein. For example, the process steps set forth above may be performed in a different order. Furthermore, no limitations are intended to the details of construction or design herein shown, other than as described in the claims below. It is therefore evident that the particular embodiments disclosed above may be altered or modified and all such variations are considered within the scope and spirit of the invention. Note that the use of terms, such as “first,” “second,” “third” or “fourth” to describe various processes or structures in this specification and in the attached claims is only used as a shorthand reference to such steps/structures and does not necessarily imply that such steps/structures are performed/formed in that ordered sequence. Of course, depending upon the exact claim language, an ordered sequence of such processes may or may not be required. Accordingly, the protection sought herein is as set forth in the claims below. 

What is claimed is:
 1. A method, comprising: detecting proximity between a mobile device and a remote device associated with a transaction reserved by a user of the mobile device, wherein detecting the proximity comprises: detecting a first location of the mobile device; extracting a verification password and a second location associated with the transaction from a document on the mobile device associated with the transaction; and comparing the first and second locations to determine the proximity; and sending the verification password to the remote device responsive to detecting the proximity.
 2. The method of claim 1, wherein detecting the proximity further comprises detecting context information associated with the device indicative of transaction engagement.
 3. The method of claim 2, wherein detecting the context information comprises detecting a transition between a walking mode of the mobile device and a driving mode of the mobile device.
 4. The method of claim 2, wherein detecting the context information further comprises: monitoring a current noise profile of the mobile device; and comparing the current noise profile to at least one reference noise profile associated with the service.
 5. The method of claim 1, wherein sending the verification password comprises sending a text message to the remote device.
 6. The method of claim 1, wherein sending the verification password comprises sending an audio message to the remote device.
 7. The method of claim 1, wherein the document comprises one of a web document, a text message, or an email message.
 8. A device, comprising: a module to detect proximity between the device and a remote device associated with a transaction reserved by a user of the device, the module comprising a location module to detect a location of the device; and a processor coupled to the module, wherein the processor is to detect a first location of the device using the location module, extract a verification password and a second location associated with the transaction from a document on the mobile device associated with the transaction, compare the first and second locations to determine the proximity and, send a verification password to the remote device responsive to detecting the proximity.
 9. The device of claim 8, wherein the module comprises a proximity communication module to communicate with the remote device to determine proximity to the remote device.
 10. The device of claim 8, wherein the processor is to detect context information associated with the device indicative of transaction engagement and send the verification password to the remote device responsive to detecting the proximity and based on the context information.
 11. The device of claim 10, further comprising a motion sensor coupled to the processor, wherein the processor is to detect the context information using data from the motion sensor to detect a transition between a walking mode of the device and a driving mode of the device.
 12. The device of claim 10, further comprising a microphone coupled to the processor, wherein the processor is to detect the context information using data from the microphone to monitor a current noise profile of the device and compare the current noise profile to at least one reference noise profile associated with the service.
 13. The device of claim 8, wherein the processor is to send the verification password by sending a text message to the remote device.
 14. The device of claim 8, wherein the processor is to send the verification password by sending an audio message to the remote device.
 15. The device of claim 1, wherein the document comprises one of a web document, a text message, or an email message.
 16. A method, comprising: detecting proximity between a mobile device and a remote device associated with a transaction reserved by a user of the mobile device, wherein detecting the proximity comprises: detecting a first location of the mobile device; receiving a second location associated with the transaction in the mobile device; comparing the first and second locations to determine the proximity; and detecting context information associated with the device indicative of transaction engagement by detecting a transition between a walking mode of the mobile device and a driving mode of the mobile device; and sending a verification password to the remote device responsive to detecting the proximity.
 17. The method of claim 16, wherein sending the verification password comprises sending a text message to the remote device.
 18. The method of claim 16, wherein sending the verification password comprises sending an audio message to the remote device.
 19. The method of claim 16, wherein the document comprises one of a web document, a text message, or an email message.
 20. The method of claim 16, wherein detecting the context information further comprises: monitoring a current noise profile of the mobile device; and comparing the current noise profile to at least one reference noise profile associated with the device. 